home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Tools (InfoMagic)
/
Internet Tools.iso
/
dos_win
/
winsock
/
hacklist
/
94-04.Z
/
94-04
/
000016_stcheng@ee.tamu.edu_Wed Apr 20 19:28:52 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-04-30
|
1KB
Received: from EE.TAMU.EDU by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA21103; Thu, 21 Apr 1994 01:27:20 -0400
Received: by ee.tamu.edu (5.61/1.34)
id AA09209; Thu, 21 Apr 94 00:28:53 -0500
From: stcheng@ee.tamu.edu (Franklin S. Cheng)
Message-Id: <9404210528.AA09209@ee.tamu.edu>
Subject: Essential Winsock problems
To: winsock-hackers@sunsite.unc.edu (WINSOCK)
Date: Thu, 21 Apr 1994 00:28:52 -0500 (CDT)
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Content-Length: 936
Dear hackers,
I have an essential winsock problem : what will happen when my
program keeps running(never return) while monitoring FD_READ by using
WSAsynchSelect(), can winsock.dll or the real TCP/IP stacks
receive the incoming packets ? My doubt is if the real IP-layer
receives packets by interrupt or from Windows 'pseudo' multitasking ?
If it's the latter, of course , not to mention it.
As I know, the DOS TCP/IP stacks receive packets via the
interrupt vector provided by packet drivers or shims. So that even
the CPU is busy in running user programs, it's still possible to
receive packets via interrupt. What about under Windows ?
Is there any way to wake up the TCP/IP stacks to receive the
incoming packets ? And because the TCP/IP stacks normally have
some amount of buffer, user programs would not lose packets then.
(if the incoming traffic is not too terrible) ,it would be nice
if it's possible.
thanks,
Franklin.